Skip to content

Instantly share code, notes, and snippets.

@mmozeiko
mmozeiko / win32_webgpu.c
Last active March 24, 2026 00:13
setting up and using WebGPU in C using Dawn
// example how to set up WebGPU rendering on Windows in C
// uses Dawn implementation of WebGPU: https://dawn.googlesource.com/dawn/
// download pre-built Dawn webgpu.h/dll/lib files from https://github.com/mmozeiko/build-dawn/releases/latest
#include "webgpu.h"
#define _CRT_SECURE_NO_DEPRECATE
#define WIN32_LEAN_AND_MEAN
#include <windows.h>
## Codebase Reality Check — Ground Truth Audit
**Purpose:** Establish what IS implemented vs what was PLANNED.
**Rule:** No assumptions. No inference from docs. Evidence from code + runtime only.
**Anti-pattern:** Reading the PRD and assuming it matches reality. It doesn't until proven.
---
### Source of truth hierarchy
@tjhanley
tjhanley / README.md
Last active March 24, 2026 00:03
Claude Code Powerline Statusline - Catppuccin Mocha

Claude Code Powerline Statusline -- Catppuccin Mocha

A powerline-style status bar for Claude Code using Catppuccin Mocha colors and Nerd Font glyphs.

Claude Code Powerline Statusline

Segments (left to right):

Segment Color Content
@muhammadyana
muhammadyana / indonesia-bank.json
Last active March 23, 2026 23:59
Daftar List Bank Indonesia Beserta Kode Bank (Json)
[
{
"name": "PT. BANK CIMB NIAGA - (CIMB)",
"code": "022"
},
{
"name": "PT. BANK CIMB NIAGA UNIT USAHA SYARIAH - (CIMB SYARIAH)",
"code": "730"
},
{
@romgerman
romgerman / ValveKeyValue.cpp
Last active March 23, 2026 23:46
Simple Valve Key Values parser in C++
#include "ValveKeyValue.h"
using namespace Parsers;
#include <exception>
#include <cctype>
ValveKeyValue::Token ValveKeyValue::LexNext()
{
bool readingValue = false;
@X-Stuff
X-Stuff / xreal_tracker_readme.md
Last active March 23, 2026 23:44
Documentation for XReal tracker for OpenTrack
@gwpl
gwpl / claude-continue-directory-migration.md
Created June 2, 2025 19:38
Claude Code `--continue` after Directory `mv` move - Migration Guide and Internal Mechanics explanation

Claude Code Continue Functionality: Directory Migration Guide ( Claude Code --continue after Directory mv move - Migration Guide and Internal Mechanics explanation )

This guide explains how to preserve Claude Code's --continue functionality when moving project directories, along with the underlying mechanics.

Note: Claude Code currently lacks built-in directory migration features. Each directory maintains independent conversation sessions, and history doesn't automatically transfer when projects are moved.

Quick Fix: Steps to Maintain Continue History

When you move a project directory and want to preserve your conversation history:

@gwpl
gwpl / claude-code-conditional-plugin-loading.md
Created March 16, 2026 21:15
Claude Code: Conditionally Loading Plugins with --plugin-dir

Claude Code: Conditionally Loading Plugins with --plugin-dir

Overview

Claude Code supports loading plugins on a per-session basis using the --plugin-dir flag. This is additive — it loads the specified plugin(s) in addition to all normally installed/enabled plugins. It does not replace them.

A plugin directory is identified by having a .claude-plugin/plugin.json manifest inside it.

Basic Usage

Claude Code Setup Audit Skill

A Claude Code skill that performs a comprehensive audit of your entire Claude Code configuration — surfacing dead weight, conflicts, stale rules, and wasted context tokens so you can keep your setup lean and effective.

Why This Exists

Claude Code configurations grow organically. You add a rule to fix a bad output, paste in a convention from a blog post, duplicate a preference across files without realizing it. Over time, your CLAUDE.md, skills, and settings accumulate cruft that eats context tokens without improving results.

This skill gives you a structured way to periodically audit everything and get an honest assessment of what to cut, merge, reword, or relocate.

@yorickdowne
yorickdowne / HallOfBlame.md
Last active March 23, 2026 23:31
Great and less great SSDs for Ethereum nodes

Overview

Syncing an Ethereum node is largely reliant on latency and IOPS, I/O Per Second, of the storage. Budget SSDs will struggle to an extent, and some won't be able to sync at all. IOPS can roughly be used as proxy of / predictor for latency. Measuring latency directly is arguably better.

This document aims to snapshot some known good and known bad models.

The drive lists are ordered by interface and then by capacity and alphabetically by vendor name, not by preference. The lists are not exhaustive at all. @mwpastore linked a filterable spreadsheet in comments that has a far greater variety of drives and their characteristics. Filter it by DRAM yes, NAND Type TLC, Form Factor M.2, and desired capacity.

For size, 4TB is a conservative choice which also supports a Fusaka "supernode". The smaller 2TB drive should last an Ethereum full node until at least sometime 2026, with [pre-merge history expiry](http